THE ORDER: 1886 FOR PC - QUICK START (LINUX)

WHAT THIS DOWNLOAD INCLUDES

"The Order 1886" (the launcher), "Play The Order 1886" (direct play), the
launcher window in bin/order1886-launcher, the dedicated compatibility
runtime and its libraries in bin, and license notices. This is unofficial,
emulator-backed compatibility software, not an official PC port.

No game executable, game archives, firmware or player saves are included.
Use your own extracted PS4 copy of The Order: 1886, in any edition:
CUSA00076 (tested), CUSA00035, CUSA00070, CUSA00100, CUSA00670 or CUSA00785
(experimental: report how they run). Update 1.02 may be applied or not.

REQUIREMENTS

- x86-64 Linux with glibc 2.39 or newer and a Vulkan driver for your GPU.
- The launcher window needs WebKitGTK 4.1 (libwebkit2gtk-4.1.so.0), for
  example the webkit2gtk-4.1 package on Arch or libwebkit2gtk-4.1-0 on
  Debian and Ubuntu. Playing does not need it.
- Extract the complete archive to a writable folder. Keep both entry points
  and bin together.

YOUR GAME FOLDER

Choose the folder that directly contains eboot.bin, archivemap.bin, _data,
sce_sys and sce_module (any folder name). The original files are only read.

WITH WEBKITGTK 4.1

Start "The Order 1886", choose your game folder on Game & Content, then press
Play. "Play The Order 1886" later starts the game directly with the saved
settings.

WITHOUT WEBKITGTK 4.1 (STEAMOS / STEAM DECK)

SteamOS does not include WebKitGTK and replaces its system files on every
update, so the launcher window cannot open there. The game still plays:

1. Put your game folder next to the extracted "The Order 1886" folder, or
   note its full path.
2. In Steam (Desktop Mode): Games > Add a Non-Steam Game, browse to
   "Play The Order 1886" and add it.
3. If the game folder is not next to the package, open the entry's
   Properties and set the launch options to:
     --game-dir "/home/deck/Games/CUSA00076"
   with your own path. It is checked and saved on the first start, so you
   can remove it afterwards.
4. Start it from Steam, in Game Mode or Desktop Mode.

Settings keep their defaults (30 FPS) until you change them in the launcher
window, for example on another PC with the same "user" folder. While playing,
F10 cycles the frame rate live: 60, 90, 120, back to 30 (rates above 60 need
a display that refreshes that fast, or VSync off). Starting
"The Order 1886" without WebKitGTK shows what is missing and then plays the
saved settings. The message is also written to
user/order1886/logs/launcher-entry.log.

To get the launcher window on SteamOS anyway, install WebKitGTK through
Homebrew and expose only its two libraries; see issue #114 on GitHub for the
exact commands.

FSR 4 (THIS INSTALLATION)

This copy was rebuilt with AMD FSR 4 support: Graphics -> Upscaling ->
AMD FSR 4 replaces the game's own temporal anti-aliasing at the game's render
size (keep Render resolution on Original 1920). FSR 3.1 is selectable on
Linux here too and is the automatic fallback. The bin/fsr4 folder must stay
beside the runtime; without it the game's own anti-aliasing stays and the
session log says why. Details: docs/verification/2026-11-08-fsr4-linux.md.

CONTROLLERS (XBOX, PLAYSTATION AND OTHER GAMEPADS)

Connect the pad before you launch, then start the game. When the runtime opens a
pad it writes "Runtime: gamepad connected: <name>" to the boot log in
user/order1886/logs and buttons work immediately. To check detection without
starting the game: bin/order1886-runtime --gamepad prints one line, either
"Gamepad: type=xbox360 ... name=..." or "Gamepad: none".

The launcher's runtime entry also prints "Order1886: pad check:" warnings when a
pad cannot work. Each has a concrete fix:

- "the running kernel has no module folder" or "visible on USB but no driver
  took it": your distribution cannot load the Xbox kernel drivers (xpad,
  hid-microsoft). This is not a game problem. The usual cause is a kernel update
  without a reboot: /lib/modules/$(uname -r) is gone, so no driver loads.
  Reboot into the installed kernel. Verify the pad reaches the kernel first:
  grep -A4 -i xbox /proc/bus/input/devices must show an event/js device;
  ls /dev/input/by-id | grep -i 045e must list the pad.
- "is present but your user cannot read it": the session grants no HID access,
  common with Bluetooth pads. Grant access once: sudo usermod -aG input $USER
  (log out and in), or install this udev rule and replug:
  echo 'KERNEL=="hidraw*", SUBSYSTEM=="hidraw", MODE="0660", GROUP="input"' \
    | sudo tee /etc/udev/rules.d/61-order1886-pad.rules
  sudo udevadm control --reload && sudo udevadm trigger
- Everything looks right but buttons do nothing in-game while the pad works
  elsewhere: Steam is grabbing the pad exclusively. Quit Steam while playing,
  or disable Steam Input for that controller family in Settings > Controllers.

Xbox pads: wired pads use xpad; Xbox Series/Elite Bluetooth pads use
hid-microsoft or xpadneo. If the pad sleeps, press the Xbox button to re-open
it. The runtime cannot use a pad that the kernel has not exposed.

UPDATING

Extract the new archive and copy your "user" folder from the old one into
it. It holds settings, saves and logs.
